Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0155

reference: 721-tree-1
name: 0155
tree-preservation-order: undefined
721-tpo-1
uprn
address-text
point: POINT (-0.989726 50.867730)
geometry: MULTIPOLYGON (((-0.989655 50.867722,-0.989658 50.867736,-0.989668 50.867749,-0.989684 50.867759,-0.989703 50.867765,-0.989725 50.867768,-0.989747 50.867766,-0.989767 50.867760,-0.989783 50.867750,-0.989793 50.867737,-0.989797 50.867723,-0.989794 50.867710,-0.989784 50.867697,-0.989769 50.867687,-0.989749 50.867680,-0.989727 50.867678,-0.989705 50.867680,-0.989685 50.867686,-0.989669 50.867696,-0.989659 50.867708,-0.989655 50.867722)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL